Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a58ad1c2066b8e0c8e2715597dbef64d94516063ff95473b43493a5baa09ddb1

Tx prefix hash: b83b7f2de4f91d46e62e5247541890c536efe38a4fabc8f54cf4a468cfac3ee9
Tx public key: b56ea8fca43d0688d464ba204913baa3a4a01ba6d19be7e57f36c50350978c04
Timestamp: 1758974904 Timestamp [UCT]: 2025-09-27 12:08:24 Age [y:d:h:m:s]: 00:010:19:43:23
Block: 1377558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7748 RingCT/type: yes/0
Extra: 01b56ea8fca43d0688d464ba204913baa3a4a01ba6d19be7e57f36c50350978c0402110000000597baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74d33a721dda8416cf5ff8ae20fa32ca6a57b09b4fb80e8d1f5b9158c86b2cee 0.600000000000 1865653 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": 1377568, "vin": [ { "gen": { "height": 1377558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74d33a721dda8416cf5ff8ae20fa32ca6a57b09b4fb80e8d1f5b9158c86b2cee" } } ], "extra": [ 1, 181, 110, 168, 252, 164, 61, 6, 136, 212, 100, 186, 32, 73, 19, 186, 163, 164, 160, 27, 166, 209, 155, 231, 229, 127, 54, 197, 3, 80, 151, 140, 4, 2, 17, 0, 0, 0, 5, 151, 186, 249, 34, 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