Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 872b6e6bc003b81d14f2ab9945eae91b304fb13831b6af86950d0dc754b7a291

Tx prefix hash: 2862c48a202b8fb7f383c4914f5df70c4eeeea462fff70b3b371abcc9acbd09e
Tx public key: 9efb9e0fc1de0229255f3636470d2689b84b1fc82e56dd6871c54a9ef3644c98
Timestamp: 1728669675 Timestamp [UCT]: 2024-10-11 18:01:15 Age [y:d:h:m:s]: 00:174:17:41:15
Block: 1129434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124662 RingCT/type: yes/0
Extra: 019efb9e0fc1de0229255f3636470d2689b84b1fc82e56dd6871c54a9ef3644c98021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ec51cbf0a0c8adad25d557419bd6dc9b447ea051785b7cd8a830198e5fd1784 0.600000000000 1612261 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": 1129444, "vin": [ { "gen": { "height": 1129434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ec51cbf0a0c8adad25d557419bd6dc9b447ea051785b7cd8a830198e5fd1784" } } ], "extra": [ 1, 158, 251, 158, 15, 193, 222, 2, 41, 37, 95, 54, 54, 71, 13, 38, 137, 184, 75, 31, 200, 46, 86, 221, 104, 113, 197, 74, 158, 243, 100, 76, 152, 2, 17, 0, 0, 0, 1, 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