Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 480e55de1b01093b93f37b91e4bb302d167a4988d6c94bb07d5b71ac6282d28e

Tx prefix hash: 28c054d2c3f030a9856241af8ab5c7031c5b7ab7915c314c3dc70e4f9eab19f0
Tx public key: 1e87837935c0062b0f875b3b5fb67df4193775212f2add271baf6a00cee92303
Timestamp: 1750273813 Timestamp [UCT]: 2025-06-18 19:10:13 Age [y:d:h:m:s]: 00:152:04:38:30
Block: 1307829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106599 RingCT/type: yes/0
Extra: 011e87837935c0062b0f875b3b5fb67df4193775212f2add271baf6a00cee92303021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56820d4ae593a8103669f66fb02bef635652f4d7ebcfe0ac416df4a4bced0055 0.600000000000 1795440 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": 1307839, "vin": [ { "gen": { "height": 1307829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56820d4ae593a8103669f66fb02bef635652f4d7ebcfe0ac416df4a4bced0055" } } ], "extra": [ 1, 30, 135, 131, 121, 53, 192, 6, 43, 15, 135, 91, 59, 95, 182, 125, 244, 25, 55, 117, 33, 47, 42, 221, 39, 27, 175, 106, 0, 206, 233, 35, 3, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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