Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8adff53f988eacec9de5b5f59ac589624644c6e4d4cc19b2aa92547966f0ec11

Tx prefix hash: e913e69896ea5f6422cfb2a1dc3848f8dab91e4aa47661ab44336f7d2b701f69
Tx public key: 01ab9d0cf18d8016922545ef65a5b2dcc9950eedd9ba0de74b570b943faa0c52
Timestamp: 1702941124 Timestamp [UCT]: 2023-12-18 23:12:04 Age [y:d:h:m:s]: 01:326:20:28:49
Block: 916127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492456 RingCT/type: yes/0
Extra: 0101ab9d0cf18d8016922545ef65a5b2dcc9950eedd9ba0de74b570b943faa0c52021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f582b45645f85fa3e586366637c0d71117e67696c68d83c27d7c0c47cb6408d1 0.600000000000 1373605 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": 916137, "vin": [ { "gen": { "height": 916127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f582b45645f85fa3e586366637c0d71117e67696c68d83c27d7c0c47cb6408d1" } } ], "extra": [ 1, 1, 171, 157, 12, 241, 141, 128, 22, 146, 37, 69, 239, 101, 165, 178, 220, 201, 149, 14, 237, 217, 186, 13, 231, 75, 87, 11, 148, 63, 170, 12, 82, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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