Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78dc4a024c42a13ca37f42b511b99bcbde499da9acb0c1e8c6f86a8a6a552a7b

Tx prefix hash: 06ffac035459e95813c586cdf6a962350e639014687cfec4eadeeff564700957
Tx public key: 4cdff7eafdfe7adda8681a5a492e662170d7a18958af06ae0499af5dadc27f5c
Timestamp: 1750556362 Timestamp [UCT]: 2025-06-22 01:39:22 Age [y:d:h:m:s]: 00:216:17:05:54
Block: 1310128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152667 RingCT/type: yes/0
Extra: 014cdff7eafdfe7adda8681a5a492e662170d7a18958af06ae0499af5dadc27f5c021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2e1d10e1daa4b22c6cee1e7fdb7c067e05313e7c3e682bc7e936e2ff163c875 0.600000000000 1797745 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": 1310138, "vin": [ { "gen": { "height": 1310128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2e1d10e1daa4b22c6cee1e7fdb7c067e05313e7c3e682bc7e936e2ff163c875" } } ], "extra": [ 1, 76, 223, 247, 234, 253, 254, 122, 221, 168, 104, 26, 90, 73, 46, 102, 33, 112, 215, 161, 137, 88, 175, 6, 174, 4, 153, 175, 93, 173, 194, 127, 92, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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