Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0a01f99a1c03a8df484f73aa8e82bae4ad0449f807e6991961242119f8144a8

Tx prefix hash: 1f9dd03028043eba448736a28668594ef127017ff076d0c782e07b6e21512b51
Tx public key: 5dcf66e0e3d63de2841b3b50391a2b96679275731ae0cefc1b6e76009c246588
Timestamp: 1735956364 Timestamp [UCT]: 2025-01-04 02:06:04 Age [y:d:h:m:s]: 00:109:04:29:56
Block: 1189720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77811 RingCT/type: yes/0
Extra: 015dcf66e0e3d63de2841b3b50391a2b96679275731ae0cefc1b6e76009c246588021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fee3b9050925a5be6e499bd8a6def5999e5043b770e1d7c19d3efda7273b87e1 0.600000000000 1676231 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": 1189730, "vin": [ { "gen": { "height": 1189720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fee3b9050925a5be6e499bd8a6def5999e5043b770e1d7c19d3efda7273b87e1" } } ], "extra": [ 1, 93, 207, 102, 224, 227, 214, 61, 226, 132, 27, 59, 80, 57, 26, 43, 150, 103, 146, 117, 115, 26, 224, 206, 252, 27, 110, 118, 0, 156, 36, 101, 136, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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