Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b93fe1eee4ce20f1b05a013af4e9a45b90a3eb186069164e148284f56283375

Tx prefix hash: 1f5d3cbdada21e80ca1c6968d78aaebf5fdda69c10e2f7c1df1038182f274331
Tx public key: e9185a7f48a401782d737846fe57e9286e55c4650d3ba11e7d4da1955a60ec72
Timestamp: 1674687473 Timestamp [UCT]: 2023-01-25 22:57:53 Age [y:d:h:m:s]: 02:002:05:48:31
Block: 682766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523239 RingCT/type: yes/0
Extra: 01e9185a7f48a401782d737846fe57e9286e55c4650d3ba11e7d4da1955a60ec720211000000035029cbac000000000000000000

1 output(s) for total of 3.355156256000 dcy

stealth address amount amount idx
00: afc7b95e8765026b691b6d5aa3e170cf243df528a5ac132a079aa4bd738f8127 3.355156256000 1124903 of 0

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": 682776, "vin": [ { "gen": { "height": 682766 } } ], "vout": [ { "amount": 3355156256, "target": { "key": "afc7b95e8765026b691b6d5aa3e170cf243df528a5ac132a079aa4bd738f8127" } } ], "extra": [ 1, 233, 24, 90, 127, 72, 164, 1, 120, 45, 115, 120, 70, 254, 87, 233, 40, 110, 85, 196, 101, 13, 59, 161, 30, 125, 77, 161, 149, 90, 96, 236, 114, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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