Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 397329be1f9368b19027d84cdb631614aa474400c5d1c9310d2aa23bd1c73cb1

Tx prefix hash: f80e8caab20089153b9814e029afc6641390e38558075005a0c5fff6ce1f3cd9
Tx public key: e5a1697bdc25886fd3ffcaefd4734b87d64de6f2feb4a3c605af9291a5d1af60
Timestamp: 1722498303 Timestamp [UCT]: 2024-08-01 07:45:03 Age [y:d:h:m:s]: 00:251:01:49:35
Block: 1078273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179339 RingCT/type: yes/0
Extra: 01e5a1697bdc25886fd3ffcaefd4734b87d64de6f2feb4a3c605af9291a5d1af60021100000012e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e62357f80c8973861673a2313f924f06725960a903bcebce7c9a6b5d4e21e61 0.600000000000 1550850 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": 1078283, "vin": [ { "gen": { "height": 1078273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e62357f80c8973861673a2313f924f06725960a903bcebce7c9a6b5d4e21e61" } } ], "extra": [ 1, 229, 161, 105, 123, 220, 37, 136, 111, 211, 255, 202, 239, 212, 115, 75, 135, 214, 77, 230, 242, 254, 180, 163, 198, 5, 175, 146, 145, 165, 209, 175, 96, 2, 17, 0, 0, 0, 18, 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