Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f80a53d493ac9370686a6ba5fd7c1b0a417e9762ce811151199309885f01f047

Tx prefix hash: 77e7cfbee7664f5e1f0ba2daed0e4d7a07da45d482e459d3aa109ece5834f5b8
Tx public key: 8418c4fc89ec1d941b0c5b5762afa986334dd341e914a7b47bf409eb6084beb5
Timestamp: 1724256484 Timestamp [UCT]: 2024-08-21 16:08:04 Age [y:d:h:m:s]: 00:231:22:17:33
Block: 1092855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165618 RingCT/type: yes/0
Extra: 018418c4fc89ec1d941b0c5b5762afa986334dd341e914a7b47bf409eb6084beb502110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb455c04caab9ba9b9a384549d6aff84be63b3a668d91ee73cefa1e24ab91f7e 0.600000000000 1567684 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": 1092865, "vin": [ { "gen": { "height": 1092855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb455c04caab9ba9b9a384549d6aff84be63b3a668d91ee73cefa1e24ab91f7e" } } ], "extra": [ 1, 132, 24, 196, 252, 137, 236, 29, 148, 27, 12, 91, 87, 98, 175, 169, 134, 51, 77, 211, 65, 233, 20, 167, 180, 123, 244, 9, 235, 96, 132, 190, 181, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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