Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6604ca4fcba70836994cf2e92f7d1458d8583333cb8891804e193a214a9c3a1

Tx prefix hash: 47ed94cfda4ec84668674ee77bfadcb568ae7b25e5c3837b7d1e4792ebcd951d
Tx public key: 865d7ce06048463fbc60f6da3a0680a2afb33c9d8269262ff0f07cf207dbc8c1
Timestamp: 1669734807 Timestamp [UCT]: 2022-11-29 15:13:27 Age [y:d:h:m:s]: 02:181:11:34:38
Block: 641747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 651442 RingCT/type: yes/0
Extra: 01865d7ce06048463fbc60f6da3a0680a2afb33c9d8269262ff0f07cf207dbc8c102110000000183600029000000000000000000

1 output(s) for total of 4.588025107000 dcy

stealth address amount amount idx
00: abe5f508fa8b012ae7fdecd1dfdd10b16832f2699b1629067664d8b048e5a11d 4.588025107000 1081572 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": 641757, "vin": [ { "gen": { "height": 641747 } } ], "vout": [ { "amount": 4588025107, "target": { "key": "abe5f508fa8b012ae7fdecd1dfdd10b16832f2699b1629067664d8b048e5a11d" } } ], "extra": [ 1, 134, 93, 124, 224, 96, 72, 70, 63, 188, 96, 246, 218, 58, 6, 128, 162, 175, 179, 60, 157, 130, 105, 38, 47, 240, 240, 124, 242, 7, 219, 200, 193, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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