Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca7c8cd41acc13879271ba869cab7a5c8d2320ad4d0fb86c6707268b1ac8026f

Tx prefix hash: bb1a3a7b96b9d498cdeebc3e1732399d98b68b1dee7d53b3c439c6e70b764d9e
Tx public key: ac3fa6bd5e702fa5b2d356f82090dd58947e9d780d3918cf3d3fc59732519e6d
Timestamp: 1763486047 Timestamp [UCT]: 2025-11-18 17:14:07 Age [y:d:h:m:s]: 00:009:16:48:15
Block: 1414951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6944 RingCT/type: yes/0
Extra: 01ac3fa6bd5e702fa5b2d356f82090dd58947e9d780d3918cf3d3fc59732519e6d0211000000018ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d0337c92e0f41aa08cfc55a52726a25f4550eec02ca261f5523efa2703c1c74 0.600000000000 1903444 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": 1414961, "vin": [ { "gen": { "height": 1414951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d0337c92e0f41aa08cfc55a52726a25f4550eec02ca261f5523efa2703c1c74" } } ], "extra": [ 1, 172, 63, 166, 189, 94, 112, 47, 165, 178, 211, 86, 248, 32, 144, 221, 88, 148, 126, 157, 120, 13, 57, 24, 207, 61, 63, 197, 151, 50, 81, 158, 109, 2, 17, 0, 0, 0, 1, 140, 235, 127, 9, 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