Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06a3dd81274f5046b67fffeb27952c1d07764b435538515604bb0b76611db9a9

Tx prefix hash: 2f883b880582cb6c6b4dfd388847ee46cfa632c849f5c30f05e801530b421c74
Tx public key: a388c9c1e1e440b53f3c2aa54d6df93c8f6da14e57941ec9c98d419d8a1a20f8
Timestamp: 1582435645 Timestamp [UCT]: 2020-02-23 05:27:25 Age [y:d:h:m:s]: 04:257:01:13:51
Block: 70651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1076257 RingCT/type: yes/0
Extra: 01a388c9c1e1e440b53f3c2aa54d6df93c8f6da14e57941ec9c98d419d8a1a20f802110000000156c366d3000000000000000000

1 output(s) for total of 358.029975496000 dcy

stealth address amount amount idx
00: 8457d985e87c0b6c61b0a6883863659d61131059899906addd58eda96c29f103 358.029975496000 130535 of 0

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": 70661, "vin": [ { "gen": { "height": 70651 } } ], "vout": [ { "amount": 358029975496, "target": { "key": "8457d985e87c0b6c61b0a6883863659d61131059899906addd58eda96c29f103" } } ], "extra": [ 1, 163, 136, 201, 193, 225, 228, 64, 181, 63, 60, 42, 165, 77, 109, 249, 60, 143, 109, 161, 78, 87, 148, 30, 201, 201, 141, 65, 157, 138, 26, 32, 248, 2, 17, 0, 0, 0, 1, 86, 195, 102, 211, 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