Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbac2d62af714c58b14dcdacbe9d2662154854ed4062194e356068ddeaaff8be

Tx prefix hash: f4c3ccbceed6784cdb6f28c102672f0544d748ce9a45f742261f6e1658ba78d1
Tx public key: e3cf9fd8ff1b5fcb1f7b8e5b250e976a76dbb9977bdc8fa98b66ed1d143df833
Timestamp: 1761549356 Timestamp [UCT]: 2025-10-27 07:15:56 Age [y:d:h:m:s]: 00:009:06:50:57
Block: 1398907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6626 RingCT/type: yes/0
Extra: 01e3cf9fd8ff1b5fcb1f7b8e5b250e976a76dbb9977bdc8fa98b66ed1d143df833021100000003df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 758a3918763a949ac9d9ddb14bc1110a1e6579bc84a38ddb584d23cd76f20773 0.600000000000 1887210 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": 1398917, "vin": [ { "gen": { "height": 1398907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "758a3918763a949ac9d9ddb14bc1110a1e6579bc84a38ddb584d23cd76f20773" } } ], "extra": [ 1, 227, 207, 159, 216, 255, 27, 95, 203, 31, 123, 142, 91, 37, 14, 151, 106, 118, 219, 185, 151, 123, 220, 143, 169, 139, 102, 237, 29, 20, 61, 248, 51, 2, 17, 0, 0, 0, 3, 223, 90, 36, 122, 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