Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c54abf44b12eeb4b87f423719e5727f87419bb0ebf25cfdb7c966c0705927fd4

Tx prefix hash: fbb4d598712c4007b5f9650c96852ff50a4fd77d80b168ff9208aa9cad6a605c
Tx public key: 0d18c9fa0cbf25dc9aca64be38e6fc0ed45d4d3665ae62eb97ab9c1ade26c177
Timestamp: 1725363358 Timestamp [UCT]: 2024-09-03 11:35:58 Age [y:d:h:m:s]: 00:251:10:54:59
Block: 1102030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179570 RingCT/type: yes/0
Extra: 010d18c9fa0cbf25dc9aca64be38e6fc0ed45d4d3665ae62eb97ab9c1ade26c17702110000000fe914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e19a48a4887dbdfbb1dcd1f68eb5ed8cba5dacf699016424954ae6a51786eb3e 0.600000000000 1578305 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": 1102040, "vin": [ { "gen": { "height": 1102030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e19a48a4887dbdfbb1dcd1f68eb5ed8cba5dacf699016424954ae6a51786eb3e" } } ], "extra": [ 1, 13, 24, 201, 250, 12, 191, 37, 220, 154, 202, 100, 190, 56, 230, 252, 14, 212, 93, 77, 54, 101, 174, 98, 235, 151, 171, 156, 26, 222, 38, 193, 119, 2, 17, 0, 0, 0, 15, 233, 20, 221, 21, 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