Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b835f3c179c6eb7061185064838034a539fe65327a831a77e45176de5a267658

Tx prefix hash: 371f56fc2e892f3c7ca523ad617f5eb4a60f08a037170e1ee9ce20df45024a71
Tx public key: 1e0c4ff0f1b4d8504c65f773da9e1730d0ca4fc17b2774bc236f3912d1106c59
Timestamp: 1726941539 Timestamp [UCT]: 2024-09-21 17:58:59 Age [y:d:h:m:s]: 00:194:03:10:28
Block: 1115106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138556 RingCT/type: yes/0
Extra: 011e0c4ff0f1b4d8504c65f773da9e1730d0ca4fc17b2774bc236f3912d1106c5902110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf9e83de8411426bb04cff63b68e6d096f3cb56af85338559506a76e51fbc185 0.600000000000 1595121 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": 1115116, "vin": [ { "gen": { "height": 1115106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf9e83de8411426bb04cff63b68e6d096f3cb56af85338559506a76e51fbc185" } } ], "extra": [ 1, 30, 12, 79, 240, 241, 180, 216, 80, 76, 101, 247, 115, 218, 158, 23, 48, 208, 202, 79, 193, 123, 39, 116, 188, 35, 111, 57, 18, 209, 16, 108, 89, 2, 17, 0, 0, 0, 13, 145, 225, 60, 4, 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