Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c2413816699aa9c4677818114cfd899033c79bf48e6d72a3b43c56a137d1921

Tx prefix hash: 9201e80d4926d79c84913d5351121db4e838a579085a3f4716c1ae7b88b3f37c
Tx public key: 0e9a5d700eefb8e00550c410a4278cc460a0dbf95be78aaf36f7d7f3e4de98ef
Timestamp: 1739584507 Timestamp [UCT]: 2025-02-15 01:55:07 Age [y:d:h:m:s]: 00:352:07:15:40
Block: 1219508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249436 RingCT/type: yes/0
Extra: 010e9a5d700eefb8e00550c410a4278cc460a0dbf95be78aaf36f7d7f3e4de98ef02110000006d8377ed96000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a8116b6b197ed721ee0f60f7161b8100573ddf3711e72a7ea342e12da3e505c 0.600000000000 1706333 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": 1219518, "vin": [ { "gen": { "height": 1219508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a8116b6b197ed721ee0f60f7161b8100573ddf3711e72a7ea342e12da3e505c" } } ], "extra": [ 1, 14, 154, 93, 112, 14, 239, 184, 224, 5, 80, 196, 16, 164, 39, 140, 196, 96, 160, 219, 249, 91, 231, 138, 175, 54, 247, 215, 243, 228, 222, 152, 239, 2, 17, 0, 0, 0, 109, 131, 119, 237, 150, 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