Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04e20546a25401fcc5ea5e869d8784f9a284e9ef775d36a995787292cb53e02c

Tx prefix hash: ce14f0c10d7790e1f1f83ef3c0731948235fde13ee271887d807b308f67fa786
Tx public key: 3840ba68d918d8e8bcc5791df9cdfa0dd59ca609ac189c4f78cba959132aa769
Timestamp: 1750347930 Timestamp [UCT]: 2025-06-19 15:45:30 Age [y:d:h:m:s]: 00:154:09:54:07
Block: 1308460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108158 RingCT/type: yes/0
Extra: 013840ba68d918d8e8bcc5791df9cdfa0dd59ca609ac189c4f78cba959132aa769021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b8784ffc4111215dcd96164957c1ab21c3ea6d3b9ff1e18932f11682e275fa1 0.600000000000 1796073 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": 1308470, "vin": [ { "gen": { "height": 1308460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b8784ffc4111215dcd96164957c1ab21c3ea6d3b9ff1e18932f11682e275fa1" } } ], "extra": [ 1, 56, 64, 186, 104, 217, 24, 216, 232, 188, 197, 121, 29, 249, 205, 250, 13, 213, 156, 166, 9, 172, 24, 156, 79, 120, 203, 169, 89, 19, 42, 167, 105, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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