Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffd15c310a355033705d62f61a71d658b6f6fcea8d7b23ff534faec08f40f9b7

Tx prefix hash: 352d8400149c78f408639de70ddae16cb5dc3c1795675c4ace41efece6688fda
Tx public key: 60e67cf4f6ea9b46f8139d91abff1b405e2e848a957edb205e90313e780db78a
Timestamp: 1735764838 Timestamp [UCT]: 2025-01-01 20:53:58 Age [y:d:h:m:s]: 00:306:10:37:31
Block: 1188119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216519 RingCT/type: yes/0
Extra: 0160e67cf4f6ea9b46f8139d91abff1b405e2e848a957edb205e90313e780db78a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd59025518ec1e0cb4530c9d76db0c8a173cf12a67fe1e3b30f072e357ef3e4b 0.600000000000 1674618 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": 1188129, "vin": [ { "gen": { "height": 1188119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd59025518ec1e0cb4530c9d76db0c8a173cf12a67fe1e3b30f072e357ef3e4b" } } ], "extra": [ 1, 96, 230, 124, 244, 246, 234, 155, 70, 248, 19, 157, 145, 171, 255, 27, 64, 94, 46, 132, 138, 149, 126, 219, 32, 94, 144, 49, 62, 120, 13, 183, 138, 2, 17, 0, 0, 0, 2, 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