Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ea466ac0eb13a8d2f0c1cd22470658d9e8595489bccf12d6cf3ad9108f8c7ac

Tx prefix hash: 4095a9a7b39519fb0267884537611d34e363579a299c8f2d05aaaff94be2b096
Tx public key: d957a7eff37e821c36cf33d02cc0a7c102f1a338cf42e079a3952ea4f99fcb33
Timestamp: 1764190789 Timestamp [UCT]: 2025-11-26 20:59:49 Age [y:d:h:m:s]: 00:000:11:54:19
Block: 1420794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357 RingCT/type: yes/0
Extra: 01d957a7eff37e821c36cf33d02cc0a7c102f1a338cf42e079a3952ea4f99fcb33021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02f6bf8ecd901f24c824e449da6998f36db2cfae8890a59d0fef5b7327aa113b 0.600000000000 1909347 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": 1420804, "vin": [ { "gen": { "height": 1420794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02f6bf8ecd901f24c824e449da6998f36db2cfae8890a59d0fef5b7327aa113b" } } ], "extra": [ 1, 217, 87, 167, 239, 243, 126, 130, 28, 54, 207, 51, 208, 44, 192, 167, 193, 2, 241, 163, 56, 207, 66, 224, 121, 163, 149, 46, 164, 249, 159, 203, 51, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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