Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ae3e6b1bf84df15c386b441df82a5ee7d6a1d4faf3f201d413aa47f60b74428

Tx prefix hash: 33d42e9a88bf1ab380e13bcd1c6e844ea968d8690f3f677938f050ed58289126
Tx public key: 36bb84e4b3dba5bf1a3188bf38add0de47163fce3d5ed6f06fd170ae599e1a59
Timestamp: 1706390700 Timestamp [UCT]: 2024-01-27 21:25:00 Age [y:d:h:m:s]: 01:028:13:38:55
Block: 944700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281475 RingCT/type: yes/0
Extra: 0136bb84e4b3dba5bf1a3188bf38add0de47163fce3d5ed6f06fd170ae599e1a5902110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b47c8e9e84e925a0d4c6944b0335f2287fcd8d43f9bc0d2b88ddfe66faeee18 0.600000000000 1402986 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": 944710, "vin": [ { "gen": { "height": 944700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b47c8e9e84e925a0d4c6944b0335f2287fcd8d43f9bc0d2b88ddfe66faeee18" } } ], "extra": [ 1, 54, 187, 132, 228, 179, 219, 165, 191, 26, 49, 136, 191, 56, 173, 208, 222, 71, 22, 63, 206, 61, 94, 214, 240, 111, 209, 112, 174, 89, 158, 26, 89, 2, 17, 0, 0, 0, 7, 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