Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 968258c329418802d31681cc8cc1ab8519b005aa62917c82f6fa6b8667f5cb28

Tx prefix hash: e8d42c58e90a191afadfba3aadd29c044fa5a1dbd8c58f8b474fed30a5abb3d6
Tx public key: afc339a1127b53629107e7b162e8f2fe10f7227326dc58df8a6c2a1601293924
Timestamp: 1711963860 Timestamp [UCT]: 2024-04-01 09:31:00 Age [y:d:h:m:s]: 00:329:20:45:55
Block: 990897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235843 RingCT/type: yes/0
Extra: 01afc339a1127b53629107e7b162e8f2fe10f7227326dc58df8a6c2a160129392402110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e80415deb0660dd3c8d9d62ee4cfa264cb9c0f55050353b5e6ce5aa47d58876 0.600000000000 1451229 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": 990907, "vin": [ { "gen": { "height": 990897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e80415deb0660dd3c8d9d62ee4cfa264cb9c0f55050353b5e6ce5aa47d58876" } } ], "extra": [ 1, 175, 195, 57, 161, 18, 123, 83, 98, 145, 7, 231, 177, 98, 232, 242, 254, 16, 247, 34, 115, 38, 220, 88, 223, 138, 108, 42, 22, 1, 41, 57, 36, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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