Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82fb7f8c4f30e9420bd050ac18dfbad9619b1f5870dca3254fd3087d2e4ba7a5

Tx prefix hash: 6a39353d7221d68f97426c1a3cb606823b5f272cc5153b204bc594964c69d85c
Tx public key: 60846144c47a41d08fab8a29be09039ea4ece48d42e216272cc58b624b127ac7
Timestamp: 1729636573 Timestamp [UCT]: 2024-10-22 22:36:13 Age [y:d:h:m:s]: 00:032:07:52:51
Block: 1137414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23086 RingCT/type: yes/0
Extra: 0160846144c47a41d08fab8a29be09039ea4ece48d42e216272cc58b624b127ac7021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1f221bb24d31b049a072c9bb30935e5e8a0bf34c9d7d15bd1b77368fae2ef7d 0.600000000000 1620899 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": 1137424, "vin": [ { "gen": { "height": 1137414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1f221bb24d31b049a072c9bb30935e5e8a0bf34c9d7d15bd1b77368fae2ef7d" } } ], "extra": [ 1, 96, 132, 97, 68, 196, 122, 65, 208, 143, 171, 138, 41, 190, 9, 3, 158, 164, 236, 228, 141, 66, 226, 22, 39, 44, 197, 139, 98, 75, 18, 122, 199, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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