Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: faee2f80feb1cd655b6f6e91c00bb61f890e3131f5d844846aaab47aa8379267

Tx prefix hash: 7f4a34b30ed6216537bd9bcb308ba62026fd8de5e1d339676efe399d0283becb
Tx public key: 48514589d1484ec0fb3be3c130fd9d83eaab950f791f43c6863c05e64c5b70a9
Timestamp: 1755372920 Timestamp [UCT]: 2025-08-16 19:35:20 Age [y:d:h:m:s]: 00:049:08:35:39
Block: 1348027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35020 RingCT/type: yes/0
Extra: 0148514589d1484ec0fb3be3c130fd9d83eaab950f791f43c6863c05e64c5b70a9021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9573d8acdf0226634b79a59df50e2e9d8595a8de76b63cfd10d8f11bca9db0b 0.600000000000 1835950 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": 1348037, "vin": [ { "gen": { "height": 1348027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9573d8acdf0226634b79a59df50e2e9d8595a8de76b63cfd10d8f11bca9db0b" } } ], "extra": [ 1, 72, 81, 69, 137, 209, 72, 78, 192, 251, 59, 227, 193, 48, 253, 157, 131, 234, 171, 149, 15, 121, 31, 67, 198, 134, 60, 5, 230, 76, 91, 112, 169, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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