Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e7330c5d41296782b54e764b00581cc1d0903291deacb74eb0334059626e27f

Tx prefix hash: 9f23c091e76df8e68c30fcb0f4f3d2a693d33960e9dccc1028d62732b57a572a
Tx public key: c50a08f6d5d3e6dad6ff5e8aca014abde3bb0676f6f17b2fdd43b2af699bc201
Timestamp: 1751698188 Timestamp [UCT]: 2025-07-05 06:49:48 Age [y:d:h:m:s]: 00:138:15:29:59
Block: 1319091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97438 RingCT/type: yes/0
Extra: 01c50a08f6d5d3e6dad6ff5e8aca014abde3bb0676f6f17b2fdd43b2af699bc201021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73714b170ccb88e5184a554c2ce431a827244c0737d47ea30525bee1c5974063 0.600000000000 1806780 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": 1319101, "vin": [ { "gen": { "height": 1319091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73714b170ccb88e5184a554c2ce431a827244c0737d47ea30525bee1c5974063" } } ], "extra": [ 1, 197, 10, 8, 246, 213, 211, 230, 218, 214, 255, 94, 138, 202, 1, 74, 189, 227, 187, 6, 118, 246, 241, 123, 47, 221, 67, 178, 175, 105, 155, 194, 1, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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