Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ea2838bde81c6851792f3831b8d006feb193aea16bd4c4430a7845544d24384

Tx prefix hash: 9e5b12042d530d96146d460cff1c9d833cef5a3ae18dbbb6d027397f2079b0ae
Tx public key: f4c20214277ee3eb3b0f4c60712caff6b599c79894a90b241f687e002c25cf20
Timestamp: 1763728636 Timestamp [UCT]: 2025-11-21 12:37:16 Age [y:d:h:m:s]: 00:031:11:37:53
Block: 1416945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22553 RingCT/type: yes/0
Extra: 01f4c20214277ee3eb3b0f4c60712caff6b599c79894a90b241f687e002c25cf20021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4afb6851e588aa1a3a38ae3ee76ccc3a1f7d770527c3ee57f095e4129d77b249 0.600000000000 1905466 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": 1416955, "vin": [ { "gen": { "height": 1416945 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4afb6851e588aa1a3a38ae3ee76ccc3a1f7d770527c3ee57f095e4129d77b249" } } ], "extra": [ 1, 244, 194, 2, 20, 39, 126, 227, 235, 59, 15, 76, 96, 113, 44, 175, 246, 181, 153, 199, 152, 148, 169, 11, 36, 31, 104, 126, 0, 44, 37, 207, 32, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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