Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fda2390c660e1b0167507a99bfbf1392772ad8b12747a6801f75190a13e5be0

Tx prefix hash: 08fda70e2323831adc3bd7795d6a3fba2b6d574f5a79b40721ec575cc98f1668
Tx public key: d48928d904ef114263e678e8b7269d333615b64f3ba15ffaa3c0055aa9e5136a
Timestamp: 1727106097 Timestamp [UCT]: 2024-09-23 15:41:37 Age [y:d:h:m:s]: 00:206:23:50:11
Block: 1116470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147765 RingCT/type: yes/0
Extra: 01d48928d904ef114263e678e8b7269d333615b64f3ba15ffaa3c0055aa9e5136a02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 964f7df8dc55c4971f69b1f46dd29bcd7e7c07cac9c4bd918b1e8990999bc2eb 0.600000000000 1596961 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": 1116480, "vin": [ { "gen": { "height": 1116470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "964f7df8dc55c4971f69b1f46dd29bcd7e7c07cac9c4bd918b1e8990999bc2eb" } } ], "extra": [ 1, 212, 137, 40, 217, 4, 239, 17, 66, 99, 230, 120, 232, 183, 38, 157, 51, 54, 21, 182, 79, 59, 161, 95, 250, 163, 192, 5, 90, 169, 229, 19, 106, 2, 17, 0, 0, 0, 1, 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