Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f56e7453c23c0ee2f468fe5dc910f8e6c9c5781fe4544693d6908a7aefc8c941

Tx prefix hash: 7d08db5261473ec8bebefcb894476e03b861135994f726e6f1e3823a441e04ac
Tx public key: 0fe7a95a9682bddf8d8f94ed295de07032f6b26750361093946b384b9fda1193
Timestamp: 1730998005 Timestamp [UCT]: 2024-11-07 16:46:45 Age [y:d:h:m:s]: 00:132:17:50:17
Block: 1148646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94720 RingCT/type: yes/0
Extra: 010fe7a95a9682bddf8d8f94ed295de07032f6b26750361093946b384b9fda11930211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a8f5f126fb71a6a9c9ef3146a3377b7e5d62ce81456fd386259f5f5503e1496 0.600000000000 1633543 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": 1148656, "vin": [ { "gen": { "height": 1148646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a8f5f126fb71a6a9c9ef3146a3377b7e5d62ce81456fd386259f5f5503e1496" } } ], "extra": [ 1, 15, 231, 169, 90, 150, 130, 189, 223, 141, 143, 148, 237, 41, 93, 224, 112, 50, 246, 178, 103, 80, 54, 16, 147, 148, 107, 56, 75, 159, 218, 17, 147, 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