Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c36040a45ef09ab634b82e4c9b0dbd69aa1f884d41c4f291eaf2dee9adb9ee8c

Tx prefix hash: 3e01e08cd7232097cad1b1f44b4b88215cfdec7defa0e8f267c8793e67452933
Tx public key: 0919f9976e063132188b20a112c7bdf41a864049e69de0faa6d67b6c9bef953d
Timestamp: 1730416499 Timestamp [UCT]: 2024-10-31 23:14:59 Age [y:d:h:m:s]: 00:082:10:31:05
Block: 1143827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58945 RingCT/type: yes/0
Extra: 010919f9976e063132188b20a112c7bdf41a864049e69de0faa6d67b6c9bef953d021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17ab86a7d74c9df3374e5c993e814cdf5ea537634eaaf62e74561604977ae220 0.600000000000 1627832 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": 1143837, "vin": [ { "gen": { "height": 1143827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17ab86a7d74c9df3374e5c993e814cdf5ea537634eaaf62e74561604977ae220" } } ], "extra": [ 1, 9, 25, 249, 151, 110, 6, 49, 50, 24, 139, 32, 161, 18, 199, 189, 244, 26, 134, 64, 73, 230, 157, 224, 250, 166, 214, 123, 108, 155, 239, 149, 61, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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