Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02592923d9209320e8b8ecd65877f40d17b292ceefe3f8938a3e29b11b8aa39b

Tx prefix hash: d64a58d05c56bf69dbef70efbf9fbaa21ec3e4fda789b7719e599be8e40e20ea
Tx public key: c01cf87d2d1085293f2e56989ad23d07c839a7b570d7ea6eb9ece560cbe5b872
Timestamp: 1764269936 Timestamp [UCT]: 2025-11-27 18:58:56 Age [y:d:h:m:s]: 00:025:05:56:50
Block: 1421456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18061 RingCT/type: yes/0
Extra: 01c01cf87d2d1085293f2e56989ad23d07c839a7b570d7ea6eb9ece560cbe5b8720211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05777d98096a969e8f2e0e9a80ceedc7c9a8e6f8db7ec472be6c43f71a67ca89 0.600000000000 1910013 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": 1421466, "vin": [ { "gen": { "height": 1421456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05777d98096a969e8f2e0e9a80ceedc7c9a8e6f8db7ec472be6c43f71a67ca89" } } ], "extra": [ 1, 192, 28, 248, 125, 45, 16, 133, 41, 63, 46, 86, 152, 154, 210, 61, 7, 200, 57, 167, 181, 112, 215, 234, 110, 185, 236, 229, 96, 203, 229, 184, 114, 2, 17, 0, 0, 0, 1, 78, 123, 252, 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