Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de186eb911c0844161227029cadb8f9adbaae9f6677e5f8cbac59f9af2535286

Tx prefix hash: 4bcbcac9ba40753d468f3558fc829765badaf1f8bb1e0cc5f019dd82998f81a2
Tx public key: 1c22736853582c3c918b471b72502b5e78ad3a66f5c1f8b90a8697563dd65291
Timestamp: 1699373261 Timestamp [UCT]: 2023-11-07 16:07:41 Age [y:d:h:m:s]: 01:335:19:27:35
Block: 886551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498862 RingCT/type: yes/0
Extra: 011c22736853582c3c918b471b72502b5e78ad3a66f5c1f8b90a8697563dd652910211000000064b8f5122000000000000000000

1 output(s) for total of 0.708742564000 dcy

stealth address amount amount idx
00: 66dc54cfdfb46304d5f58ef9233247e7d6bda8ebb975f1cef26ee1c1639952d4 0.708742564000 1342378 of 0

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": 886561, "vin": [ { "gen": { "height": 886551 } } ], "vout": [ { "amount": 708742564, "target": { "key": "66dc54cfdfb46304d5f58ef9233247e7d6bda8ebb975f1cef26ee1c1639952d4" } } ], "extra": [ 1, 28, 34, 115, 104, 83, 88, 44, 60, 145, 139, 71, 27, 114, 80, 43, 94, 120, 173, 58, 102, 245, 193, 248, 185, 10, 134, 151, 86, 61, 214, 82, 145, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 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