Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fa39b1ddae5a327dfb21d5362150156d7e7500deea02eae2dc67333103fd94a

Tx prefix hash: 1eebbddcb0012219e875432d9482539edb5ea0846dd90a7dd147c55556f57d24
Tx public key: 296c1034e59b67f8d6a3a2f642933b1f337a29825205264b22585247f16c3d9e
Timestamp: 1698782972 Timestamp [UCT]: 2023-10-31 20:09:32 Age [y:d:h:m:s]: 01:144:16:29:11
Block: 881866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364392 RingCT/type: yes/0
Extra: 01296c1034e59b67f8d6a3a2f642933b1f337a29825205264b22585247f16c3d9e02110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.734533947000 dcy

stealth address amount amount idx
00: 8174d654aa52a708a16ca92da40b0b5ee2ab2690a169033f0f81394de21264b3 0.734533947000 1337488 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": 881876, "vin": [ { "gen": { "height": 881866 } } ], "vout": [ { "amount": 734533947, "target": { "key": "8174d654aa52a708a16ca92da40b0b5ee2ab2690a169033f0f81394de21264b3" } } ], "extra": [ 1, 41, 108, 16, 52, 229, 155, 103, 248, 214, 163, 162, 246, 66, 147, 59, 31, 51, 122, 41, 130, 82, 5, 38, 75, 34, 88, 82, 71, 241, 108, 61, 158, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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