Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f153b0002e1eff854b0b0665499cc9c636bd07ace8e6518d568b8abde36b2e21

Tx prefix hash: a0ce8e024a11bd16726c4637ff63886ea3f28e67ffe8df74ec09d4fbd820f5ee
Tx public key: 6aa0b5e371e9414ef0fe3c8af5b8931e00a7cdd4ee9c8223a61220acf6892a07
Timestamp: 1634690985 Timestamp [UCT]: 2021-10-20 00:49:45 Age [y:d:h:m:s]: 03:070:11:24:05
Block: 356510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 828491 RingCT/type: yes/0
Extra: 016aa0b5e371e9414ef0fe3c8af5b8931e00a7cdd4ee9c8223a61220acf6892a070211000000013fc41461000000000000000000

1 output(s) for total of 40.432890506000 dcy

stealth address amount amount idx
00: 8d71e246c4e361ecf26f97dec6892bf242768e25e9f083b2b002835db187985b 40.432890506000 727366 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 356520, "vin": [ { "gen": { "height": 356510 } } ], "vout": [ { "amount": 40432890506, "target": { "key": "8d71e246c4e361ecf26f97dec6892bf242768e25e9f083b2b002835db187985b" } } ], "extra": [ 1, 106, 160, 181, 227, 113, 233, 65, 78, 240, 254, 60, 138, 245, 184, 147, 30, 0, 167, 205, 212, 238, 156, 130, 35, 166, 18, 32, 172, 246, 137, 42, 7, 2, 17, 0, 0, 0, 1, 63, 196, 20, 97, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8