Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9fa0feba644e850a929d009352a3a7cf816a961ed21e647c543df001526b1bf

Tx prefix hash: 60c53b5da3e15ffa32ec3a5c9ca974e66e058e5bea8163a209310a61536dc202
Tx public key: abbaa0bc726b309dea7a948408dfeda83cb649aa34203cb0a0e9741837172f0f
Timestamp: 1710252896 Timestamp [UCT]: 2024-03-12 14:14:56 Age [y:d:h:m:s]: 01:061:07:36:23
Block: 976761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304824 RingCT/type: yes/0
Extra: 01abbaa0bc726b309dea7a948408dfeda83cb649aa34203cb0a0e9741837172f0f0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa5d2f2bd1207d55e1c74e549c5e9361601f2df9f83462621f878b5bd9521b28 0.600000000000 1436758 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": 976771, "vin": [ { "gen": { "height": 976761 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa5d2f2bd1207d55e1c74e549c5e9361601f2df9f83462621f878b5bd9521b28" } } ], "extra": [ 1, 171, 186, 160, 188, 114, 107, 48, 157, 234, 122, 148, 132, 8, 223, 237, 168, 60, 182, 73, 170, 52, 32, 60, 176, 160, 233, 116, 24, 55, 23, 47, 15, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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