Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94f0c635046bb8a739e494f307ac88eae811a46f4b8b5541ca2dde0aad0c541b

Tx prefix hash: f2250c2a6890ba1a4296f02d8f14dd6cc9fd6c31dca093c2912f16e4797e64d8
Tx public key: a76146df2f40c6a14307c2d3dfe77d81fb6ab4de9fd8ccc7b7f18b33281c205b
Timestamp: 1739215608 Timestamp [UCT]: 2025-02-10 19:26:48 Age [y:d:h:m:s]: 00:030:20:52:24
Block: 1216421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22105 RingCT/type: yes/0
Extra: 01a76146df2f40c6a14307c2d3dfe77d81fb6ab4de9fd8ccc7b7f18b33281c205b021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 464bf89ab2da9706c041d50e1aed589be86b27b3b6918f80cafa2b9f616c4115 0.600000000000 1703226 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": 1216431, "vin": [ { "gen": { "height": 1216421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "464bf89ab2da9706c041d50e1aed589be86b27b3b6918f80cafa2b9f616c4115" } } ], "extra": [ 1, 167, 97, 70, 223, 47, 64, 198, 161, 67, 7, 194, 211, 223, 231, 125, 129, 251, 106, 180, 222, 159, 216, 204, 199, 183, 241, 139, 51, 40, 28, 32, 91, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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