Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c704f097d8e916b7519095cf4b9f0b11b9757345ba86c35dd9b45288b145d3c0

Tx prefix hash: bdb287b8985c7dc92af8369cd770b2e5480f2f3f0c5f67ea2d15dea4456b5e6a
Tx public key: c3ec0fe0c7392a7ee1e44d85921ec813fc80560adb3b8a5c025324d29ba56ac0
Timestamp: 1737201131 Timestamp [UCT]: 2025-01-18 11:52:11 Age [y:d:h:m:s]: 00:153:08:41:41
Block: 1200010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109268 RingCT/type: yes/0
Extra: 01c3ec0fe0c7392a7ee1e44d85921ec813fc80560adb3b8a5c025324d29ba56ac00211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83b2fcee0d37ca33c58cb3b4ce4df272e4ed6c8892e1b61e5e9b306bd189a3e0 0.600000000000 1686651 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": 1200020, "vin": [ { "gen": { "height": 1200010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83b2fcee0d37ca33c58cb3b4ce4df272e4ed6c8892e1b61e5e9b306bd189a3e0" } } ], "extra": [ 1, 195, 236, 15, 224, 199, 57, 42, 126, 225, 228, 77, 133, 146, 30, 200, 19, 252, 128, 86, 10, 219, 59, 138, 92, 2, 83, 36, 210, 155, 165, 106, 192, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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