Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 452a4a69da207da5a8679519fda1c751a3d5e3cf448795b35d5625cb6f81edc2

Tx prefix hash: 83953f55b097757f3884901bd71c68f57e372bfa50e83aef492225bc4e9ca74f
Tx public key: 5635bda7da7df26eeb105a14e57af56633a8ee419a720ebbe59e7b8a4939e0e3
Timestamp: 1602481414 Timestamp [UTC]: 2020-10-12 05:43:34 Age [y:d:h:m:s]: 06:039:16:10:21
Block: 140833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1541360 RingCT/type: yes/0
Extra: 015635bda7da7df26eeb105a14e57af56633a8ee419a720ebbe59e7b8a4939e0e30211000000ebf4b4cc44000000000000000000

1 output(s) for total of 0.209586117490 xmr

stealth address amount amount idx tag
00: b4a34db2afd8d4cacb7c08dad0e418bbb4b2d474da1ec16141e5122684a3c251 0.209586117490 233860 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": 140843, "vin": [ { "gen": { "height": 140833 } } ], "vout": [ { "amount": 209586117490, "target": { "key": "b4a34db2afd8d4cacb7c08dad0e418bbb4b2d474da1ec16141e5122684a3c251" } } ], "extra": [ 1, 86, 53, 189, 167, 218, 125, 242, 110, 235, 16, 90, 20, 229, 122, 245, 102, 51, 168, 238, 65, 154, 114, 14, 187, 229, 158, 123, 138, 73, 57, 224, 227, 2, 17, 0, 0, 0, 235, 244, 180, 204, 68, 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) | monero version: