Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3de9c7ca285e6989663acbff3703f39d3e903a1d51a19a2ae925037b760377df

Tx prefix hash: 5533effb55fd263fd25840a2cfb0eb692923bf18b0bbb7ef7f361aa29f1922da
Tx public key: d48465ceb953653eac3ecbf68f332d5cf0a1f6c36f654c6eaaba15c44278c69a
Timestamp: 1737624617 Timestamp [UCT]: 2025-01-23 09:30:17 Age [y:d:h:m:s]: 00:301:17:36:54
Block: 1203473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213188 RingCT/type: yes/0
Extra: 01d48465ceb953653eac3ecbf68f332d5cf0a1f6c36f654c6eaaba15c44278c69a021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7abb19d6136d0b2e3106bc5e130fe7fa14ccb6a283c0c72f09e9dc557a11557 0.600000000000 1690150 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": 1203483, "vin": [ { "gen": { "height": 1203473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7abb19d6136d0b2e3106bc5e130fe7fa14ccb6a283c0c72f09e9dc557a11557" } } ], "extra": [ 1, 212, 132, 101, 206, 185, 83, 101, 62, 172, 62, 203, 246, 143, 51, 45, 92, 240, 161, 246, 195, 111, 101, 76, 110, 170, 186, 21, 196, 66, 120, 198, 154, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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