Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cae566d66e4da6814d5ac0c8581066148f55f7449c5bb3762f81b21089cef02

Tx prefix hash: 1f7f8eb2ddcb28964b49713df559fb6feddf014c8ae2523aeabe9bb9c4f28365
Tx public key: b322dd60b8911ec865917016a01ce6692da4d86af8d927e9d16c29930b33acec
Timestamp: 1736618236 Timestamp [UCT]: 2025-01-11 17:57:16 Age [y:d:h:m:s]: 00:064:18:32:12
Block: 1195184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46085 RingCT/type: yes/0
Extra: 01b322dd60b8911ec865917016a01ce6692da4d86af8d927e9d16c29930b33acec0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c784e4d51ea98472edbc817c7b0e1272f2e41fe034e7d2e5b5f273ec6b33ad7b 0.600000000000 1681773 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": 1195194, "vin": [ { "gen": { "height": 1195184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c784e4d51ea98472edbc817c7b0e1272f2e41fe034e7d2e5b5f273ec6b33ad7b" } } ], "extra": [ 1, 179, 34, 221, 96, 184, 145, 30, 200, 101, 145, 112, 22, 160, 28, 230, 105, 45, 164, 216, 106, 248, 217, 39, 233, 209, 108, 41, 147, 11, 51, 172, 236, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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