Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 511276f2bbaea3ff8d1733f8c4b0da326a0ff11f6f7cc7792b58d7e92d87e82f

Tx prefix hash: 28c18b07ec48adb25dd90f92ab4d3c6c2dc452bfa5feeb4bd09f3f126a7737b5
Tx public key: 204106ae612d5d39abb213074954ad8b60cfe00cb940d5c63de900b560c9017c
Timestamp: 1577008429 Timestamp [UTC]: 2019-12-22 09:53:49 Age [y:d:h:m:s]: 06:059:04:01:24
Block: 29581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1450223 RingCT/type: yes/0
Extra: 01204106ae612d5d39abb213074954ad8b60cfe00cb940d5c63de900b560c9017c02110000000d4ac5aa02000000000000000000

1 output(s) for total of 0.489763854529 xmr

stealth address amount amount idx tag
00: c781f070af07df4fbc71578f17e8eba08cee518e97ec69976af5a2a6501ebbb2 0.489763854529 48667 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 dinastycoin-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": 29591, "vin": [ { "gen": { "height": 29581 } } ], "vout": [ { "amount": 489763854529, "target": { "key": "c781f070af07df4fbc71578f17e8eba08cee518e97ec69976af5a2a6501ebbb2" } } ], "extra": [ 1, 32, 65, 6, 174, 97, 45, 93, 57, 171, 178, 19, 7, 73, 84, 173, 139, 96, 207, 224, 12, 185, 64, 213, 198, 61, 233, 0, 181, 96, 201, 1, 124, 2, 17, 0, 0, 0, 13, 74, 197, 170, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369