Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d98bfdc39d459004c7629266d97228d2b322694667b48c3d9afa64e249f15922

Tx prefix hash: bfdea3a8f70184fd31b3d8b07d2a1d037224c5cecbf8ffd821de0df31cb7c86d
Tx public key: c44f81b5d28d10cb132ae1ae34a327e1bac49cbda53b40a7f12258fdab9d9e3f
Timestamp: 1704501174 Timestamp [UCT]: 2024-01-06 00:32:54 Age [y:d:h:m:s]: 01:112:14:29:28
Block: 929040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341618 RingCT/type: yes/0
Extra: 01c44f81b5d28d10cb132ae1ae34a327e1bac49cbda53b40a7f12258fdab9d9e3f0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c760c17acde5c36fa8c7fd2155e4f9f7e511e87241562ec8bbadeb24c371b3c5 0.600000000000 1386908 of 15

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": 929050, "vin": [ { "gen": { "height": 929040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c760c17acde5c36fa8c7fd2155e4f9f7e511e87241562ec8bbadeb24c371b3c5" } } ], "extra": [ 1, 196, 79, 129, 181, 210, 141, 16, 203, 19, 42, 225, 174, 52, 163, 39, 225, 186, 196, 156, 189, 165, 59, 64, 167, 241, 34, 88, 253, 171, 157, 158, 63, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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