Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 652764672a6464da7abba9a99973d172b4084dac1521332f3a301b76e352f085

Tx prefix hash: aab941b386cc964d69fda371de164a048758524db8d9904abba404d2243b3180
Tx public key: 59f3a37177947f9a3055f8dc1aa748ae86cf1f02c84804d03307a34e42f100e7
Timestamp: 1583238754 Timestamp [UCT]: 2020-03-03 12:32:34 Age [y:d:h:m:s]: 04:268:20:57:27
Block: 75638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1086383 RingCT/type: yes/0
Extra: 0159f3a37177947f9a3055f8dc1aa748ae86cf1f02c84804d03307a34e42f100e702110000019903d36d11000000000000000000

1 output(s) for total of 344.651921023000 dcy

stealth address amount amount idx
00: 02a8ac15110f0ea8a3d1c837f182886ef3c01f5a5bd642f1a752524c137e12f5 344.651921023000 139594 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": 75648, "vin": [ { "gen": { "height": 75638 } } ], "vout": [ { "amount": 344651921023, "target": { "key": "02a8ac15110f0ea8a3d1c837f182886ef3c01f5a5bd642f1a752524c137e12f5" } } ], "extra": [ 1, 89, 243, 163, 113, 119, 148, 127, 154, 48, 85, 248, 220, 26, 167, 72, 174, 134, 207, 31, 2, 200, 72, 4, 208, 51, 7, 163, 78, 66, 241, 0, 231, 2, 17, 0, 0, 1, 153, 3, 211, 109, 17, 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