Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23a9228c39398ba39163eae2c422c41ed0ddec2c613b129a6b92f3bbefb123e5

Tx prefix hash: ae84a9559c3cbc71cdd487b0efaa1832412b7c1f3c755a9bd3bee469df417bee
Tx public key: 6a3adf22fed9637dcc812a398b72c1bec805e111b2a27ae324d5dd8ff9cda40d
Timestamp: 1738169170 Timestamp [UCT]: 2025-01-29 16:46:10 Age [y:d:h:m:s]: 00:140:20:41:26
Block: 1207773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100620 RingCT/type: yes/0
Extra: 016a3adf22fed9637dcc812a398b72c1bec805e111b2a27ae324d5dd8ff9cda40d0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07792b3f717b929b7889b6de772c949a151d24ec9528dbbe262b1ab5c6bab1f9 0.600000000000 1694498 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": 1207783, "vin": [ { "gen": { "height": 1207773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07792b3f717b929b7889b6de772c949a151d24ec9528dbbe262b1ab5c6bab1f9" } } ], "extra": [ 1, 106, 58, 223, 34, 254, 217, 99, 125, 204, 129, 42, 57, 139, 114, 193, 190, 200, 5, 225, 17, 178, 162, 122, 227, 36, 213, 221, 143, 249, 205, 164, 13, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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