Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dc864be12e2286cd31ca0f856af851f82cf7af61aa4dec6dde7634d9ca5f04e

Tx prefix hash: 8945fa6b9fc041768b135b940d530e350de431d58fdd0b6ce9539cedfbe96b2b
Tx public key: de0654c5d9a074ce5894193c62dc4118e9169fb32994a2fba2af207a606dc87e
Timestamp: 1702523297 Timestamp [UCT]: 2023-12-14 03:08:17 Age [y:d:h:m:s]: 01:182:02:33:26
Block: 912664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391279 RingCT/type: yes/0
Extra: 01de0654c5d9a074ce5894193c62dc4118e9169fb32994a2fba2af207a606dc87e02110000000633af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f275e61302ba213c67ae2f0a3fa2a660e34dd0546e5dddbcaf76a4cce9e8ec72 0.600000000000 1369896 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": 912674, "vin": [ { "gen": { "height": 912664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f275e61302ba213c67ae2f0a3fa2a660e34dd0546e5dddbcaf76a4cce9e8ec72" } } ], "extra": [ 1, 222, 6, 84, 197, 217, 160, 116, 206, 88, 148, 25, 60, 98, 220, 65, 24, 233, 22, 159, 179, 41, 148, 162, 251, 162, 175, 32, 122, 96, 109, 200, 126, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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