Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdb67672e99e7a80d661be3e0cfebc41e7de81c47aeedae9cf6f9dcef36929be

Tx prefix hash: d5d5cf0d883a15f19a361f5988db5a36ef06ae7946fd24fb077699019c300313
Tx public key: 819783e000eca2a1f4ca660b8a476415f06a0dc574d6d1efa0dce23e766c6108
Timestamp: 1720527498 Timestamp [UCT]: 2024-07-09 12:18:18 Age [y:d:h:m:s]: 00:280:19:38:38
Block: 1061934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200630 RingCT/type: yes/0
Extra: 01819783e000eca2a1f4ca660b8a476415f06a0dc574d6d1efa0dce23e766c6108021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f07410af6a399a057c2d901a96bcaaaf439248f6a80cef948b27657a3333e869 0.600000000000 1532433 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": 1061944, "vin": [ { "gen": { "height": 1061934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f07410af6a399a057c2d901a96bcaaaf439248f6a80cef948b27657a3333e869" } } ], "extra": [ 1, 129, 151, 131, 224, 0, 236, 162, 161, 244, 202, 102, 11, 138, 71, 100, 21, 240, 106, 13, 197, 116, 214, 209, 239, 160, 220, 226, 62, 118, 108, 97, 8, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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