Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e80a6dd7e167801811e72f26ba950fde799789f423898c89ac240103f4cab44

Tx prefix hash: 534ca4248ebcfa8669a07108293f6148c7b49fbffb6ad9f6fdc8dd45db555961
Tx public key: 55b3b052abb3b336ea1e42f3c9e7c8d5248853aaec5fe9db7a3b3c0858724f2c
Timestamp: 1721342124 Timestamp [UCT]: 2024-07-18 22:35:24 Age [y:d:h:m:s]: 00:128:15:27:48
Block: 1068697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92040 RingCT/type: yes/0
Extra: 0155b3b052abb3b336ea1e42f3c9e7c8d5248853aaec5fe9db7a3b3c0858724f2c02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6760725605b45d5f0efc0b51b5f57b8bf3c4a6988569a021a8f9b2bbd883d4c 0.600000000000 1539826 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": 1068707, "vin": [ { "gen": { "height": 1068697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6760725605b45d5f0efc0b51b5f57b8bf3c4a6988569a021a8f9b2bbd883d4c" } } ], "extra": [ 1, 85, 179, 176, 82, 171, 179, 179, 54, 234, 30, 66, 243, 201, 231, 200, 213, 36, 136, 83, 170, 236, 95, 233, 219, 122, 59, 60, 8, 88, 114, 79, 44, 2, 17, 0, 0, 0, 9, 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