Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cea474d3f273ff475a7e9db074e043f5c93c64fd5846ca7c8d7d6e04ea6bbbc8

Tx prefix hash: 47144143fdfb17eedd25db782324e34f179edf062322bb69b30823e2e9ceba38
Tx public key: 8be9bd359a9c9136fb750ae33f6cee248b46c83dcfc55d81f4b9aa0f9fa916e4
Timestamp: 1743542419 Timestamp [UCT]: 2025-04-01 21:20:19 Age [y:d:h:m:s]: 00:271:20:16:46
Block: 1252228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192085 RingCT/type: yes/0
Extra: 018be9bd359a9c9136fb750ae33f6cee248b46c83dcfc55d81f4b9aa0f9fa916e40211000000024060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 434bf7fb6a2bf64fe76419963e21994e1c192c5b7fa01e5f62921044d8930c3b 0.600000000000 1739307 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": 1252238, "vin": [ { "gen": { "height": 1252228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "434bf7fb6a2bf64fe76419963e21994e1c192c5b7fa01e5f62921044d8930c3b" } } ], "extra": [ 1, 139, 233, 189, 53, 154, 156, 145, 54, 251, 117, 10, 227, 63, 108, 238, 36, 139, 70, 200, 61, 207, 197, 93, 129, 244, 185, 170, 15, 159, 169, 22, 228, 2, 17, 0, 0, 0, 2, 64, 96, 246, 210, 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