Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 946e8057009c402abcb12a81c339fee55555969b5c43e816f69a27e8f44781c4

Tx prefix hash: 3f6d2609874d7369840cc0e5c987db8e05cd282219946fc8ff87fc8884056fcd
Tx public key: 0644ca70bc3eceaebcbd13dc63c4fa13f3a6eae6a8d072de8b2bf19f3f1a6068
Timestamp: 1719456178 Timestamp [UCT]: 2024-06-27 02:42:58 Age [y:d:h:m:s]: 00:263:08:27:40
Block: 1053040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188194 RingCT/type: yes/0
Extra: 010644ca70bc3eceaebcbd13dc63c4fa13f3a6eae6a8d072de8b2bf19f3f1a606802110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e52d758eb1c5f1283330e8b3d782aab3ce72ed48a4889972c901583255e1708c 0.600000000000 1523385 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": 1053050, "vin": [ { "gen": { "height": 1053040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e52d758eb1c5f1283330e8b3d782aab3ce72ed48a4889972c901583255e1708c" } } ], "extra": [ 1, 6, 68, 202, 112, 188, 62, 206, 174, 188, 189, 19, 220, 99, 196, 250, 19, 243, 166, 234, 230, 168, 208, 114, 222, 139, 43, 241, 159, 63, 26, 96, 104, 2, 17, 0, 0, 0, 5, 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