Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24fd1b3cbfac7aa788d68e76fe993e59dbc1ec6d4de6c5631e1e0311f670a0b7

Tx prefix hash: a05e2404889df2b75a37cc2c4adfffe805b5eda3e35644a0322ec6a6481a3c57
Tx public key: 8f9ec646754cfa5d4fd40e5f40c0e26672d6e8267146595cced1cfe346456605
Timestamp: 1723916801 Timestamp [UCT]: 2024-08-17 17:46:41 Age [y:d:h:m:s]: 00:219:03:27:38
Block: 1090033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156479 RingCT/type: yes/0
Extra: 018f9ec646754cfa5d4fd40e5f40c0e26672d6e8267146595cced1cfe34645660502110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72c8f7c7cccc36950fe98b1a49d24c6ed19042102580bb214ddb1aaeb30c8b18 0.600000000000 1564656 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": 1090043, "vin": [ { "gen": { "height": 1090033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72c8f7c7cccc36950fe98b1a49d24c6ed19042102580bb214ddb1aaeb30c8b18" } } ], "extra": [ 1, 143, 158, 198, 70, 117, 76, 250, 93, 79, 212, 14, 95, 64, 192, 226, 102, 114, 214, 232, 38, 113, 70, 89, 92, 206, 209, 207, 227, 70, 69, 102, 5, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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