Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e4c391db790469cfb2d0186c2c8ae1be13b191b61608b48f32d9e7e4751b371

Tx prefix hash: ff73a835ae5a30888b8ad5ad495243b966f30c809ffa38957f18c45bd5394c38
Tx public key: 848a01fb94ce7a3302bc4f7e98ba258412aef29c54dc223410fe4e63043f36e2
Timestamp: 1751613565 Timestamp [UCT]: 2025-07-04 07:19:25 Age [y:d:h:m:s]: 00:140:08:36:13
Block: 1318455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98588 RingCT/type: yes/0
Extra: 01848a01fb94ce7a3302bc4f7e98ba258412aef29c54dc223410fe4e63043f36e2021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81239d0f9aa0fb0adf8b826681143c7e5b99d11ea3667df405cc14b20a873841 0.600000000000 1806136 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": 1318465, "vin": [ { "gen": { "height": 1318455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81239d0f9aa0fb0adf8b826681143c7e5b99d11ea3667df405cc14b20a873841" } } ], "extra": [ 1, 132, 138, 1, 251, 148, 206, 122, 51, 2, 188, 79, 126, 152, 186, 37, 132, 18, 174, 242, 156, 84, 220, 34, 52, 16, 254, 78, 99, 4, 63, 54, 226, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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