Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38aed7efd18eb1c893ec657c00d379f8c0862d6f971db6a5a7ff4f679c06fbf0

Tx prefix hash: c09a209fd47f112c056b21a43b631e625ee21227e26b554a5fde459108d26660
Tx public key: f4ff9c59966a1b9ebd0b2a4204ad8db27490770a1f2e118b400de13622b52570
Timestamp: 1723784686 Timestamp [UCT]: 2024-08-16 05:04:46 Age [y:d:h:m:s]: 01:085:16:17:27
Block: 1088930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319700 RingCT/type: yes/0
Extra: 01f4ff9c59966a1b9ebd0b2a4204ad8db27490770a1f2e118b400de13622b52570021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cf212dac3d3f6e6e91786974f216ba7d5e5b48f440ebe003c76ecf1087e7389 0.600000000000 1563549 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": 1088940, "vin": [ { "gen": { "height": 1088930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cf212dac3d3f6e6e91786974f216ba7d5e5b48f440ebe003c76ecf1087e7389" } } ], "extra": [ 1, 244, 255, 156, 89, 150, 106, 27, 158, 189, 11, 42, 66, 4, 173, 141, 178, 116, 144, 119, 10, 31, 46, 17, 139, 64, 13, 225, 54, 34, 181, 37, 112, 2, 17, 0, 0, 0, 3, 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