Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89a7556d49af506fc975d1ca8e9be43929a5938db2ab4e291414d6b5a37d0264

Tx prefix hash: c836d0bd54e3f8a4e60f8762186d806bd3d4539f87bc87f36c727b3bd344ee3c
Tx public key: 29b8d8b4a2d8f5ccdba0d827b72db5962ffbea1464dcc5ea3eeacfc4d810b447
Timestamp: 1681280462 Timestamp [UCT]: 2023-04-12 06:21:02 Age [y:d:h:m:s]: 02:044:10:18:35
Block: 736776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 553970 RingCT/type: yes/0
Extra: 0129b8d8b4a2d8f5ccdba0d827b72db5962ffbea1464dcc5ea3eeacfc4d810b4470211000000015029cbac000000000000000000

1 output(s) for total of 2.222058479000 dcy

stealth address amount amount idx
00: d295ca5a5e64562d2bc7f169638a89e5c43afb6f11908c66eee77e30ceb3c2e5 2.222058479000 1183245 of 0

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": 736786, "vin": [ { "gen": { "height": 736776 } } ], "vout": [ { "amount": 2222058479, "target": { "key": "d295ca5a5e64562d2bc7f169638a89e5c43afb6f11908c66eee77e30ceb3c2e5" } } ], "extra": [ 1, 41, 184, 216, 180, 162, 216, 245, 204, 219, 160, 216, 39, 183, 45, 181, 150, 47, 251, 234, 20, 100, 220, 197, 234, 62, 234, 207, 196, 216, 16, 180, 71, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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