Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca8ae6b6a1586317f100337944d982d03148c8b0a45f829df7029074ed4f6ec3

Tx prefix hash: d6fadf234aab6e4649ca647fa1400a24dc4007190564b5705d528d2aec70c38a
Tx public key: 0aea520c0931da899677db799061df984b2e50f801776b3ee5a6d1077684c60a
Timestamp: 1745394952 Timestamp [UCT]: 2025-04-23 07:55:52 Age [y:d:h:m:s]: 00:211:16:41:45
Block: 1267575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149012 RingCT/type: yes/0
Extra: 010aea520c0931da899677db799061df984b2e50f801776b3ee5a6d1077684c60a021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b02f82e7f78c6a81b33c0a2636dbef2c7613f376a4c8110dcde4ae9089a230e 0.600000000000 1754804 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": 1267585, "vin": [ { "gen": { "height": 1267575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b02f82e7f78c6a81b33c0a2636dbef2c7613f376a4c8110dcde4ae9089a230e" } } ], "extra": [ 1, 10, 234, 82, 12, 9, 49, 218, 137, 150, 119, 219, 121, 144, 97, 223, 152, 75, 46, 80, 248, 1, 119, 107, 62, 229, 166, 209, 7, 118, 132, 198, 10, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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