Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e5e462a09c1db358b7a9bbb881e2a9961c4abf1f7c84a2bf20f6d306b95297e

Tx prefix hash: 29a5978dccb958e553eedfea15d6d7dfa637332822c989d7065db2356651269e
Tx public key: 15ab0d6283a82c71459a29b07d822a2beab6102ccd2edd7a45e5cb92d579bc05
Timestamp: 1708372011 Timestamp [UCT]: 2024-02-19 19:46:51 Age [y:d:h:m:s]: 01:117:09:09:30
Block: 961154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344867 RingCT/type: yes/0
Extra: 0115ab0d6283a82c71459a29b07d822a2beab6102ccd2edd7a45e5cb92d579bc050211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97b0a0c9717595ae6b1c008599a3b3686f22eb8c5d74eda9b066c0510211bceb 0.600000000000 1420741 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": 961164, "vin": [ { "gen": { "height": 961154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97b0a0c9717595ae6b1c008599a3b3686f22eb8c5d74eda9b066c0510211bceb" } } ], "extra": [ 1, 21, 171, 13, 98, 131, 168, 44, 113, 69, 154, 41, 176, 125, 130, 42, 43, 234, 182, 16, 44, 205, 46, 221, 122, 69, 229, 203, 146, 213, 121, 188, 5, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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