Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1de837559c2f109648835b892b4521c6e30bcfafbbd0143bcfec852668036014

Tx prefix hash: d9cf04693d4fd5dd32930aa3cb28a313a8c12aaee13b2e33cd792daf7f35e8b2
Tx public key: f2200f6f9957e2bf567de5d7fb61a8ff0a4115d0704f1539f085644c03852d62
Timestamp: 1744372153 Timestamp [UCT]: 2025-04-11 11:49:13 Age [y:d:h:m:s]: 00:256:04:33:58
Block: 1259124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180847 RingCT/type: yes/0
Extra: 01f2200f6f9957e2bf567de5d7fb61a8ff0a4115d0704f1539f085644c03852d620211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48c3eea54cbcb0ab39a46228187e92b185e92b5c6bece9d36f36efb219a3fa5f 0.600000000000 1746263 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": 1259134, "vin": [ { "gen": { "height": 1259124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48c3eea54cbcb0ab39a46228187e92b185e92b5c6bece9d36f36efb219a3fa5f" } } ], "extra": [ 1, 242, 32, 15, 111, 153, 87, 226, 191, 86, 125, 229, 215, 251, 97, 168, 255, 10, 65, 21, 208, 112, 79, 21, 57, 240, 133, 100, 76, 3, 133, 45, 98, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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