Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ff2136bc004a661d1e408fbdd690bab9ac4ed48e353c1f3e31b2a22574535e5

Tx prefix hash: 0ae3c3534a432f4abc63d2ee0f1bfc04ff3c73056e1111ff5dca21e178658700
Tx public key: 55b810862c90c266e7e5a0514c95748f8ef1d83438363a9238ea76d214dae8ca
Timestamp: 1735342561 Timestamp [UCT]: 2024-12-27 23:36:01 Age [y:d:h:m:s]: 00:100:11:42:51
Block: 1184615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71614 RingCT/type: yes/0
Extra: 0155b810862c90c266e7e5a0514c95748f8ef1d83438363a9238ea76d214dae8ca0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ace50c777d201216222301dd4032d4da4dfacb395c8aa857e1e48f9cb57ac83d 0.600000000000 1671074 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": 1184625, "vin": [ { "gen": { "height": 1184615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ace50c777d201216222301dd4032d4da4dfacb395c8aa857e1e48f9cb57ac83d" } } ], "extra": [ 1, 85, 184, 16, 134, 44, 144, 194, 102, 231, 229, 160, 81, 76, 149, 116, 143, 142, 241, 216, 52, 56, 54, 58, 146, 56, 234, 118, 210, 20, 218, 232, 202, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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