Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b45b7cbe3f6450d6d0470a94736de42cd59dd6e3cc04e79169866c2b3eea1643

Tx prefix hash: 6b58e416e13f059ddcb10bd29958dc6bc6d582ca65cf6eef47e15ca50707557b
Tx public key: 8841a1e03d5c2a3eb5a163ce54c50afda3de1119b9069effa283adf1ded09a3f
Timestamp: 1696805607 Timestamp [UCT]: 2023-10-08 22:53:27 Age [y:d:h:m:s]: 01:090:03:37:28
Block: 865471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325687 RingCT/type: yes/0
Extra: 018841a1e03d5c2a3eb5a163ce54c50afda3de1119b9069effa283adf1ded09a3f0211000000044b8f5122000000000000000000

1 output(s) for total of 0.832406259000 dcy

stealth address amount amount idx
00: ff511d624a87f8fe259aec7ed9e3a4661964756bdbe80983ed485a7e528024c3 0.832406259000 1320007 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": 865481, "vin": [ { "gen": { "height": 865471 } } ], "vout": [ { "amount": 832406259, "target": { "key": "ff511d624a87f8fe259aec7ed9e3a4661964756bdbe80983ed485a7e528024c3" } } ], "extra": [ 1, 136, 65, 161, 224, 61, 92, 42, 62, 181, 161, 99, 206, 84, 197, 10, 253, 163, 222, 17, 25, 185, 6, 158, 255, 162, 131, 173, 241, 222, 208, 154, 63, 2, 17, 0, 0, 0, 4, 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