Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b74807fedcf4e2424b4ba8c6cdf356ff1d014857341fedece6214bdc47825f34

Tx prefix hash: b8dccae24ef4000366c6b32323b36851072bc0a717628b83f026cbaa84b61ab3
Tx public key: 66a2e92646f1f2ad0893f3e35c649fd0a36b177c09035d8d787f538e70d1d3a3
Timestamp: 1679512604 Timestamp [UCT]: 2023-03-22 19:16:44 Age [y:d:h:m:s]: 02:073:03:01:36
Block: 722792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 573836 RingCT/type: yes/0
Extra: 0166a2e92646f1f2ad0893f3e35c649fd0a36b177c09035d8d787f538e70d1d3a30211000000035029cbac000000000000000000

1 output(s) for total of 2.472236071000 dcy

stealth address amount amount idx
00: 9bb6d1c2229baf01376046c1e620f6d9d94fc5ebc032c61901d899752784b6d8 2.472236071000 1167743 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": 722802, "vin": [ { "gen": { "height": 722792 } } ], "vout": [ { "amount": 2472236071, "target": { "key": "9bb6d1c2229baf01376046c1e620f6d9d94fc5ebc032c61901d899752784b6d8" } } ], "extra": [ 1, 102, 162, 233, 38, 70, 241, 242, 173, 8, 147, 243, 227, 92, 100, 159, 208, 163, 107, 23, 124, 9, 3, 93, 141, 120, 127, 83, 142, 112, 209, 211, 163, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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