Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbe75e235aafe587a8952015608e20a3e12784fa4cbb1bd16a9775c56e5e0450

Tx prefix hash: 9a5c839894fab5b8e94375a273c71448b8b4535975debfb089b68f42d8e4a2b6
Tx public key: 947e4968d7761e006a09c7d042809d89a713792c56fc02b75efca98a0b10c18b
Timestamp: 1673891051 Timestamp [UCT]: 2023-01-16 17:44:11 Age [y:d:h:m:s]: 02:102:06:39:49
Block: 676147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594789 RingCT/type: yes/0
Extra: 01947e4968d7761e006a09c7d042809d89a713792c56fc02b75efca98a0b10c18b0211000000038b7b6602000000000000000000

1 output(s) for total of 3.528939844000 dcy

stealth address amount amount idx
00: 69e3ac562615d0bc8f4ab0672ebe7c7495ea3f0ec07f16b20cde7d34e1c3067b 3.528939844000 1117856 of 0

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": 676157, "vin": [ { "gen": { "height": 676147 } } ], "vout": [ { "amount": 3528939844, "target": { "key": "69e3ac562615d0bc8f4ab0672ebe7c7495ea3f0ec07f16b20cde7d34e1c3067b" } } ], "extra": [ 1, 148, 126, 73, 104, 215, 118, 30, 0, 106, 9, 199, 208, 66, 128, 157, 137, 167, 19, 121, 44, 86, 252, 2, 183, 94, 252, 169, 138, 11, 16, 193, 139, 2, 17, 0, 0, 0, 3, 139, 123, 102, 2, 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