Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 513dd5066ce7f9dc8b6a8667d70773f84687b6dcdb79835d241ffbe594e91ffd

Tx prefix hash: 66ad1680a564df7a2dd052b89ee7e4e02264d42a4ecbe3566f693892f901a3e6
Tx public key: 40fa7573cf01784059d66d551c131831d85c84a9fa68f8e2f434258799f49ce9
Timestamp: 1723324072 Timestamp [UCT]: 2024-08-10 21:07:52 Age [y:d:h:m:s]: 00:166:22:30:53
Block: 1085121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119368 RingCT/type: yes/0
Extra: 0140fa7573cf01784059d66d551c131831d85c84a9fa68f8e2f434258799f49ce902110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 395a7b5905cbaea6c4a3ac21d4735e3309c7c8942a0ddf1683b6b269cdd4d66a 0.600000000000 1559626 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": 1085131, "vin": [ { "gen": { "height": 1085121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "395a7b5905cbaea6c4a3ac21d4735e3309c7c8942a0ddf1683b6b269cdd4d66a" } } ], "extra": [ 1, 64, 250, 117, 115, 207, 1, 120, 64, 89, 214, 109, 85, 28, 19, 24, 49, 216, 92, 132, 169, 250, 104, 248, 226, 244, 52, 37, 135, 153, 244, 156, 233, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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