Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d89277be743ef9483bbc77813c458f046776769736e2b661a059f291385c6928

Tx prefix hash: 6f16bb02a258ea574654256f305a067037bd00cd639cf829aa5073725abfd4a0
Tx public key: f3349c40b8b2b903646ce024ca11ca5e9e7d2820314045d746245b8a9e08bfb4
Timestamp: 1721191878 Timestamp [UCT]: 2024-07-17 04:51:18 Age [y:d:h:m:s]: 00:252:02:01:33
Block: 1067450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180058 RingCT/type: yes/0
Extra: 01f3349c40b8b2b903646ce024ca11ca5e9e7d2820314045d746245b8a9e08bfb402110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 030ae432ef0bb3b7cf92c9101f4e023413b500a3df21e88a5c81fa941bdcc954 0.600000000000 1538263 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": 1067460, "vin": [ { "gen": { "height": 1067450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "030ae432ef0bb3b7cf92c9101f4e023413b500a3df21e88a5c81fa941bdcc954" } } ], "extra": [ 1, 243, 52, 156, 64, 184, 178, 185, 3, 100, 108, 224, 36, 202, 17, 202, 94, 158, 125, 40, 32, 49, 64, 69, 215, 70, 36, 91, 138, 158, 8, 191, 180, 2, 17, 0, 0, 0, 2, 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