Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcf411c75908c9098984718cfe4c944ee41e7aedb771fda59bdae9222c259b83

Tx prefix hash: 3375907ed58eb72fe2cf142d7d6bf047c2f41f85c6e11e8524362d0b2256b811
Tx public key: 8edc273dd6f2eec17dd31fb1099afab8dbd1e38c8d68951d490d857216742ff2
Timestamp: 1710462470 Timestamp [UCT]: 2024-03-15 00:27:50 Age [y:d:h:m:s]: 00:297:08:37:35
Block: 978507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212852 RingCT/type: yes/0
Extra: 018edc273dd6f2eec17dd31fb1099afab8dbd1e38c8d68951d490d857216742ff20211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1f5c7c3bbe8e9e7fe3fb663a5c82340376d844be29f1f52543832e0be9bc6e9 0.600000000000 1438534 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": 978517, "vin": [ { "gen": { "height": 978507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1f5c7c3bbe8e9e7fe3fb663a5c82340376d844be29f1f52543832e0be9bc6e9" } } ], "extra": [ 1, 142, 220, 39, 61, 214, 242, 238, 193, 125, 211, 31, 177, 9, 154, 250, 184, 219, 209, 227, 140, 141, 104, 149, 29, 73, 13, 133, 114, 22, 116, 47, 242, 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