Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 623120a3711360f8a5898f5c92513e479dbd5f092437ec6db54a4aaefb982ab1

Tx prefix hash: 191c48fb70378c605f88e88431f9ed368604a7c10c8de25590d24c0974474b48
Tx public key: b4f5b10ee84e14ae53499da3d08feb65a275419d6eb95264dc6b3caf06c73c27
Timestamp: 1757069938 Timestamp [UCT]: 2025-09-05 10:58:58 Age [y:d:h:m:s]: 00:107:17:15:13
Block: 1361858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77043 RingCT/type: yes/0
Extra: 01b4f5b10ee84e14ae53499da3d08feb65a275419d6eb95264dc6b3caf06c73c27021100000004ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a151f88b0964a57689bd6853fcc6ca14acd7171c20fa976d5cdd8e6214fcf057 0.600000000000 1849881 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": 1361868, "vin": [ { "gen": { "height": 1361858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a151f88b0964a57689bd6853fcc6ca14acd7171c20fa976d5cdd8e6214fcf057" } } ], "extra": [ 1, 180, 245, 177, 14, 232, 78, 20, 174, 83, 73, 157, 163, 208, 143, 235, 101, 162, 117, 65, 157, 110, 185, 82, 100, 220, 107, 60, 175, 6, 199, 60, 39, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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