Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f4c42849632cf9470a77dbd508346f19c7c1f42a3a9262c319358bc43f02217

Tx prefix hash: b6a6342ff16f8404722fb420a2530b890457880f19a298f71c3ae93e37689309
Tx public key: 903dc2ea323ea35acd177fcd9a1f825bb42249be20a45d06c58ef1460f037a8d
Timestamp: 1716921888 Timestamp [UCT]: 2024-05-28 18:44:48 Age [y:d:h:m:s]: 01:163:19:45:41
Block: 1032044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375663 RingCT/type: yes/0
Extra: 01903dc2ea323ea35acd177fcd9a1f825bb42249be20a45d06c58ef1460f037a8d021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d357fcd152dae5c1efcc56250ec7617f51d89e21da27a26cf08187d2a1cbc31 0.600000000000 1500493 of 15

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": 1032054, "vin": [ { "gen": { "height": 1032044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d357fcd152dae5c1efcc56250ec7617f51d89e21da27a26cf08187d2a1cbc31" } } ], "extra": [ 1, 144, 61, 194, 234, 50, 62, 163, 90, 205, 23, 127, 205, 154, 31, 130, 91, 180, 34, 73, 190, 32, 164, 93, 6, 197, 142, 241, 70, 15, 3, 122, 141, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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