Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a2a863a02ce8fc9f05f17b3fc5aef4509d9bd335cac7fe737215941e6f42aee

Tx prefix hash: ab8494005408f6da6dce9597035e19963164ee5d60cb2bfabcb9132b883cf1a9
Tx public key: 1b9a306a2bcdba0571614feee1ea30506e7584bc92c96dd06bdb21da4c3aa0d2
Timestamp: 1731366312 Timestamp [UCT]: 2024-11-11 23:05:12 Age [y:d:h:m:s]: 00:193:23:08:01
Block: 1151691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138494 RingCT/type: yes/0
Extra: 011b9a306a2bcdba0571614feee1ea30506e7584bc92c96dd06bdb21da4c3aa0d20211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5861a7c8f2e97160059029a299a30a7e98fcc130ef9d24266ed22e7d7a577e32 0.600000000000 1637268 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": 1151701, "vin": [ { "gen": { "height": 1151691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5861a7c8f2e97160059029a299a30a7e98fcc130ef9d24266ed22e7d7a577e32" } } ], "extra": [ 1, 27, 154, 48, 106, 43, 205, 186, 5, 113, 97, 79, 238, 225, 234, 48, 80, 110, 117, 132, 188, 146, 201, 109, 208, 107, 219, 33, 218, 76, 58, 160, 210, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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