Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e4c88bde89e4891ccdb0f2a598e705aa0d69d712ff4f3d4b920c82956c371e2

Tx prefix hash: c80e59e0a8b98398c11f709639c5db16783f0b4f3dbbf90168c9441ecf4b5e23
Tx public key: 8233da081434b215f6a140cb199d1fe7287263de2f8648cc681deb4238102770
Timestamp: 1709227620 Timestamp [UCT]: 2024-02-29 17:27:00 Age [y:d:h:m:s]: 01:019:12:58:14
Block: 968256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274978 RingCT/type: yes/0
Extra: 018233da081434b215f6a140cb199d1fe7287263de2f8648cc681deb423810277002110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4790409b66fdc7a5f717b68208e8d09c4143e23c2fe8d963d988e9d5cb63af43 0.600000000000 1428059 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": 968266, "vin": [ { "gen": { "height": 968256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4790409b66fdc7a5f717b68208e8d09c4143e23c2fe8d963d988e9d5cb63af43" } } ], "extra": [ 1, 130, 51, 218, 8, 20, 52, 178, 21, 246, 161, 64, 203, 25, 157, 31, 231, 40, 114, 99, 222, 47, 134, 72, 204, 104, 29, 235, 66, 56, 16, 39, 112, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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