Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8459eb1a4b78d270f53f5be9c306de233b57c1d10eb945071fbbf55e2bb24d37

Tx prefix hash: c887544152ffc39456d67495f76b44657f3f6e2b9242817cbfca642e060063eb
Tx public key: 3cbc36ae9e32ce104c32ff2c7e2921298e72fb94d2f29d7539b84face0289d90
Timestamp: 1709338149 Timestamp [UCT]: 2024-03-02 00:09:09 Age [y:d:h:m:s]: 00:328:23:26:48
Block: 969170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235439 RingCT/type: yes/0
Extra: 013cbc36ae9e32ce104c32ff2c7e2921298e72fb94d2f29d7539b84face0289d9002110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d63e18d5e3cb6a2c9d15e6d791617a3b3ea45f0fca702eae43138ba5bab06d1e 0.600000000000 1428999 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": 969180, "vin": [ { "gen": { "height": 969170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d63e18d5e3cb6a2c9d15e6d791617a3b3ea45f0fca702eae43138ba5bab06d1e" } } ], "extra": [ 1, 60, 188, 54, 174, 158, 50, 206, 16, 76, 50, 255, 44, 126, 41, 33, 41, 142, 114, 251, 148, 210, 242, 157, 117, 57, 184, 79, 172, 224, 40, 157, 144, 2, 17, 0, 0, 0, 2, 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