Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e30243128e8539216c5f7c595b25beef116bcd1c42636c299c1bc4c66476a735

Tx prefix hash: d4e40509ea70d202daf8fab499681035a3ec8d34efda50370a6e0875ec516b5a
Tx public key: a723fb23fda6f24d262939c6e362b1a20c35c48731e77382e1bad37fc7bb84a5
Timestamp: 1730091984 Timestamp [UCT]: 2024-10-28 05:06:24 Age [y:d:h:m:s]: 00:168:11:18:14
Block: 1141146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120249 RingCT/type: yes/0
Extra: 01a723fb23fda6f24d262939c6e362b1a20c35c48731e77382e1bad37fc7bb84a502110000000e007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 364c9554518e57d95504d9c7f69a44114baf43e7d771135bc0be649e7ec0643b 0.600000000000 1624953 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": 1141156, "vin": [ { "gen": { "height": 1141146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "364c9554518e57d95504d9c7f69a44114baf43e7d771135bc0be649e7ec0643b" } } ], "extra": [ 1, 167, 35, 251, 35, 253, 166, 242, 77, 38, 41, 57, 198, 227, 98, 177, 162, 12, 53, 196, 135, 49, 231, 115, 130, 225, 186, 211, 127, 199, 187, 132, 165, 2, 17, 0, 0, 0, 14, 0, 127, 151, 138, 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