Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3abd9bb8b3e3377bf761626c6f67381855b97d82826bf7ce12022dd256451c76

Tx prefix hash: 1e2021a53cdc2cf6c0f743bc9fb2d2e7af42e741c39ed7eaf1c416432eb60406
Tx public key: d6b84140f8f46813a25e599a69e3905d74ec7fa2d506441a807d991b92a76e8f
Timestamp: 1716423634 Timestamp [UCT]: 2024-05-23 00:20:34 Age [y:d:h:m:s]: 00:337:01:05:48
Block: 1027906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240911 RingCT/type: yes/0
Extra: 01d6b84140f8f46813a25e599a69e3905d74ec7fa2d506441a807d991b92a76e8f02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b57cbe5d2b75eeecd3794e08f4100195a2cd99667399a38711fdd64f7f1136e8 0.600000000000 1495781 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": 1027916, "vin": [ { "gen": { "height": 1027906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b57cbe5d2b75eeecd3794e08f4100195a2cd99667399a38711fdd64f7f1136e8" } } ], "extra": [ 1, 214, 184, 65, 64, 248, 244, 104, 19, 162, 94, 89, 154, 105, 227, 144, 93, 116, 236, 127, 162, 213, 6, 68, 26, 128, 125, 153, 27, 146, 167, 110, 143, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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