Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24a99e845343824fe30831e2a371644c8ec8e0471b3459ca0d4eb62a56e2ff68

Tx prefix hash: 34ec93a023526da235c52bc031cfb07b1ae23e5e330dd86a5a2a604801312c70
Tx public key: aa58faf1cf8a05c74c0aa645c52423f947ebb9dfcb7204c46c4d175750778793
Timestamp: 1708259516 Timestamp [UCT]: 2024-02-18 12:31:56 Age [y:d:h:m:s]: 01:263:19:25:44
Block: 960223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 447292 RingCT/type: yes/0
Extra: 01aa58faf1cf8a05c74c0aa645c52423f947ebb9dfcb7204c46c4d17575077879302110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cb5867347b72728a1235edbca0bc7e21ecb9243b6e2819c85b9a6143fb25e87 0.600000000000 1419786 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": 960233, "vin": [ { "gen": { "height": 960223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cb5867347b72728a1235edbca0bc7e21ecb9243b6e2819c85b9a6143fb25e87" } } ], "extra": [ 1, 170, 88, 250, 241, 207, 138, 5, 199, 76, 10, 166, 69, 197, 36, 35, 249, 71, 235, 185, 223, 203, 114, 4, 196, 108, 77, 23, 87, 80, 119, 135, 147, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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