Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 459024d9c3681328d20cb62613c90c4d48f5876d4f60db22575d8420b2a42d33

Tx prefix hash: 0e936e89f67cbcc3370288f13f9b4dcad5b5481f3c02fddfae81ed418009febf
Tx public key: 5151dfa101f741b201409f352cd97b3e11efa1920a1178e7ec5e45db82e6e8fd
Timestamp: 1700487886 Timestamp [UCT]: 2023-11-20 13:44:46 Age [y:d:h:m:s]: 01:180:04:19:55
Block: 895783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389982 RingCT/type: yes/0
Extra: 015151dfa101f741b201409f352cd97b3e11efa1920a1178e7ec5e45db82e6e8fd0211000000014b8f5122000000000000000000

1 output(s) for total of 0.660539895000 dcy

stealth address amount amount idx
00: a794f0390271eb480172bfa182a62d859b3b584d28d92aa72894031182af3ca7 0.660539895000 1352030 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": 895793, "vin": [ { "gen": { "height": 895783 } } ], "vout": [ { "amount": 660539895, "target": { "key": "a794f0390271eb480172bfa182a62d859b3b584d28d92aa72894031182af3ca7" } } ], "extra": [ 1, 81, 81, 223, 161, 1, 247, 65, 178, 1, 64, 159, 53, 44, 217, 123, 62, 17, 239, 161, 146, 10, 17, 120, 231, 236, 94, 69, 219, 130, 230, 232, 253, 2, 17, 0, 0, 0, 1, 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