Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dcd895fd070170001994524a3c0e9444ce723ce5f291e02accfeab1e5ab38e0

Tx prefix hash: 62871c14569961a00344c815adfcef3a8bb9e4c3aedb2695ce7e1ecc5de49563
Tx public key: 5873d06ed9a23d303f8a61f5bfe3e757d8ee4dcccfc53ae2de4ca2c8fe7ef9da
Timestamp: 1635565516 Timestamp [UCT]: 2021-10-30 03:45:16 Age [y:d:h:m:s]: 03:007:19:30:55
Block: 363381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 784013 RingCT/type: yes/0
Extra: 015873d06ed9a23d303f8a61f5bfe3e757d8ee4dcccfc53ae2de4ca2c8fe7ef9da02110000005d42b3953e000000000000000000

1 output(s) for total of 38.367924283000 dcy

stealth address amount amount idx
00: 0f81ae09fb2f65e71b7ac9d0fa8be8745752c0ee753749ce62ecd239c0d0a6be 38.367924283000 738571 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": 363391, "vin": [ { "gen": { "height": 363381 } } ], "vout": [ { "amount": 38367924283, "target": { "key": "0f81ae09fb2f65e71b7ac9d0fa8be8745752c0ee753749ce62ecd239c0d0a6be" } } ], "extra": [ 1, 88, 115, 208, 110, 217, 162, 61, 48, 63, 138, 97, 245, 191, 227, 231, 87, 216, 238, 77, 204, 207, 197, 58, 226, 222, 76, 162, 200, 254, 126, 249, 218, 2, 17, 0, 0, 0, 93, 66, 179, 149, 62, 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