Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bef3adcce2a32893543ed0e7488003bd176c0ced4d49ed33e7712bf347b1e02

Tx prefix hash: 006808aa0569aab59470ae4be622ec8f809e9ec61b74826e8fab382a696cc8bd
Tx public key: 41f1d84d8b7cb1544e9d07a987d2d9ba44038e88c1937d46e0cd0f9561dadb20
Timestamp: 1717044545 Timestamp [UCT]: 2024-05-30 04:49:05 Age [y:d:h:m:s]: 00:242:01:53:53
Block: 1033052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173016 RingCT/type: yes/0
Extra: 0141f1d84d8b7cb1544e9d07a987d2d9ba44038e88c1937d46e0cd0f9561dadb2002110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec5c584aa0a126e90c059c2d8527a3a62414932d352698f0e98dc3e3bb2ee396 0.600000000000 1501509 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": 1033062, "vin": [ { "gen": { "height": 1033052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec5c584aa0a126e90c059c2d8527a3a62414932d352698f0e98dc3e3bb2ee396" } } ], "extra": [ 1, 65, 241, 216, 77, 139, 124, 177, 84, 78, 157, 7, 169, 135, 210, 217, 186, 68, 3, 142, 136, 193, 147, 125, 70, 224, 205, 15, 149, 97, 218, 219, 32, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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