Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00572fa6d3e403398edb354cd643209ed554a291684d87015318f408a19318a2

Tx prefix hash: dac0f362dd9cc08e5d2d79367f1941a637dac174c2bf582ee1b00a4d38f94307
Tx public key: a7a255e20b203472f325b465aa312a9a7660f00a596b7d00bc064c07233acc51
Timestamp: 1755022718 Timestamp [UCT]: 2025-08-12 18:18:38 Age [y:d:h:m:s]: 00:100:20:46:05
Block: 1345602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71418 RingCT/type: yes/0
Extra: 01a7a255e20b203472f325b465aa312a9a7660f00a596b7d00bc064c07233acc51021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 889c8ea9bb7abd149c19d94f2db8f3c758b5dde0225601e2d3483381c3ddcff2 0.600000000000 1833497 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": 1345612, "vin": [ { "gen": { "height": 1345602 } } ], "vout": [ { "amount": 600000000, "target": { "key": "889c8ea9bb7abd149c19d94f2db8f3c758b5dde0225601e2d3483381c3ddcff2" } } ], "extra": [ 1, 167, 162, 85, 226, 11, 32, 52, 114, 243, 37, 180, 101, 170, 49, 42, 154, 118, 96, 240, 10, 89, 107, 125, 0, 188, 6, 76, 7, 35, 58, 204, 81, 2, 17, 0, 0, 0, 4, 228, 220, 144, 9, 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