Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07ef75a1cb9d639c72a7395b5a93f689e08295707c4ecb187c49e1aa63e158a5

Tx prefix hash: 927f11937923f6e65b35602b1bc5c0db19d72371c85df4e1e532ae0b2a22007c
Tx public key: c3c814a31742e35bd698bcd2bd09692f6577ee78ddc442b15c249a06c5f78a59
Timestamp: 1706138760 Timestamp [UCT]: 2024-01-24 23:26:00 Age [y:d:h:m:s]: 01:289:19:30:24
Block: 942611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 465944 RingCT/type: yes/0
Extra: 01c3c814a31742e35bd698bcd2bd09692f6577ee78ddc442b15c249a06c5f78a5902110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0155e324f03b2a3dfbb1aab8f6655c13f62290ec8bd40ee572a33f71ca104586 0.600000000000 1400785 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": 942621, "vin": [ { "gen": { "height": 942611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0155e324f03b2a3dfbb1aab8f6655c13f62290ec8bd40ee572a33f71ca104586" } } ], "extra": [ 1, 195, 200, 20, 163, 23, 66, 227, 91, 214, 152, 188, 210, 189, 9, 105, 47, 101, 119, 238, 120, 221, 196, 66, 177, 92, 36, 154, 6, 197, 247, 138, 89, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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