Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd5e29525f3686ce179c55c4f120132c66d6ab1c2b4fed65794a8e20abe48675

Tx prefix hash: a517db29a883c79b2ae90a41a53b51ba2adbbc67e25b135cc8d2fe32a4e5d752
Tx public key: e0e9e9e330528f0b44282a1f8387a9197f5af1c1f99a796c3eef7f1dfa779226
Timestamp: 1736238668 Timestamp [UCT]: 2025-01-07 08:31:08 Age [y:d:h:m:s]: 00:084:03:59:50
Block: 1192052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59916 RingCT/type: yes/0
Extra: 01e0e9e9e330528f0b44282a1f8387a9197f5af1c1f99a796c3eef7f1dfa7792260211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cb468f0afe51f3c90091f889b535f8decccd13f1a403f94a2877283b1e0a951 0.600000000000 1678597 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": 1192062, "vin": [ { "gen": { "height": 1192052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cb468f0afe51f3c90091f889b535f8decccd13f1a403f94a2877283b1e0a951" } } ], "extra": [ 1, 224, 233, 233, 227, 48, 82, 143, 11, 68, 40, 42, 31, 131, 135, 169, 25, 127, 90, 241, 193, 249, 154, 121, 108, 62, 239, 127, 29, 250, 119, 146, 38, 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