Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a74205423c5abf370ede0cb957d660a1ffa45e30550e572ade91d074edb389fe

Tx prefix hash: bf00b3bddf98216e23b070d2b6952b8826fe0f2f028367dafd650ce582905f02
Tx public key: eac17d5e1c050dc769d33eae1f13ad4e64f718129bc9b24754d47462b89a547e
Timestamp: 1755237506 Timestamp [UCT]: 2025-08-15 05:58:26 Age [y:d:h:m:s]: 00:096:21:24:22
Block: 1347034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68935 RingCT/type: yes/0
Extra: 01eac17d5e1c050dc769d33eae1f13ad4e64f718129bc9b24754d47462b89a547e021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b86906e8b58eb7b1b5bab1a1d6aed8d4f6058291cf757c8e96c38355b21608c4 0.600000000000 1834947 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": 1347044, "vin": [ { "gen": { "height": 1347034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b86906e8b58eb7b1b5bab1a1d6aed8d4f6058291cf757c8e96c38355b21608c4" } } ], "extra": [ 1, 234, 193, 125, 94, 28, 5, 13, 199, 105, 211, 62, 174, 31, 19, 173, 78, 100, 247, 24, 18, 155, 201, 178, 71, 84, 212, 116, 98, 184, 154, 84, 126, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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